Using Lists, Tables, and Callouts
Plain paragraphs are the default output of most writers — and most AI tools. But web readers don't read paragraphs. They scan. Lists, tables, and callouts are the three structural elements that transform a wall of text into a scannable, engaging, and snippet-eligible page. Using them well increases dwell time. Using them poorly (or not at all) pushes readers to competitors who format better than you.
Part 1 — When to Use Each Element
The Decision Framework
The choice between paragraph, list, table, and callout is never arbitrary. Each has a purpose.
flowchart TD
A[Information to Present] --> B{What type of info?}
B -- Sequence / Steps --> C[Numbered List]
B -- Options / Features --> D[Bulleted List]
B -- Comparison / Multi-Dimension --> E[Table]
B -- Warning / Emphasis --> F[Callout / Admonition]
B -- Explanation / Narrative --> G[Paragraph]
B -- Definition / Single Stat --> H[Callout + Paragraph]
style C fill:#1A3557,color:#fff
style D fill:#1A3557,color:#fff
style E fill:#1A3557,color:#fff
style F fill:#1A3557,color:#fff
- Lists
- Tables
- Callouts / Admonitions
| Use When | Type | Example |
|---|---|---|
| Steps in a process | Numbered list | "How to set up your account: 1. Register. 2. Verify email. 3. Configure settings." |
| Features or options (no order) | Bulleted list | "Benefits include: faster load times, better indexing, improved UX." |
| 3–7 items of equal importance | Bulleted list | "Top metrics to track: bounce rate, dwell time, CTR, pogo-sticking." |
| More than 7 items | Consider a table instead | Lists longer than 7 items lose scannability |
Rules:
- Each list item starts with a bold keyword or action verb
- Each item is 1–2 lines maximum
- Parallel structure: all items use the same grammatical form
| Use When | Why Tables Win | Example |
|---|---|---|
| Comparing 2+ items on 3+ dimensions | Side-by-side comparison is instantly scannable | Tool comparison: features, pricing, best-for |
| Showing data with multiple attributes | Rows × columns organize multi-attribute data | Keyword reports: volume, KD, CPC, intent |
| Mapping relationships | Two-axis relationships are clearer in grid form | Hook formula × content type compatibility |
Rules:
- 3–5 columns maximum (more = hard to read on mobile)
- Clear, concise column headers
- Consistent formatting within each column
- Align numerical data right; text data left
| Use When | Callout Type | Signal to Reader |
|---|---|---|
| Critical information | :::warning | "This could break something. Read carefully." |
| Helpful tip | :::tip | "This optional technique will save you time." |
| Key takeaway | :::important | "This is the ONE thing to remember from this section." |
| Background context | :::info | "This is supplementary context, not essential to the process." |
| Danger / risk | :::caution | "Doing this wrong has serious consequences." |
Rules:
- Maximum 1 callout per 500 words — overuse dilutes impact
- Never stack two callouts consecutively
- Callout text should be 1–3 sentences, not full paragraphs
Part 2 — The Formatting Rhythm
Breaking the Monotone
A well-formatted article alternates between element types. A poorly formatted one uses the same element repeatedly (or only paragraphs).
- ❌ Monotone Rhythm
- ✅ Dynamic Rhythm
Paragraph → Paragraph → Paragraph → Paragraph → Paragraph
The reader's eye finds no anchor points. Every section looks the same. Scanning fails because nothing stands out. This is the default output of both inexperienced writers and unguided AI.
Paragraph → List → Paragraph → Table → Callout →
Paragraph → Diagram → Paragraph → List → Callout
Every 200–300 words, the reader encounters a different visual element. Their eye has anchor points. The page feels dynamic and alive. Sections are visually distinct, making it easy to find specific information.
The 300-Word Rule
If you have 300+ consecutive words of paragraph text with no list, table, callout, or visual — the section needs reformatting. This is not an arbitrary number; it's the approximate scroll depth where scanners lose patience.
Part 3 — Common Formatting Mistakes
| Mistake | Why It's Bad | Fix |
|---|---|---|
| Bullet-point everything | Lists lose impact when overused. The article reads like notes, not content | Use lists only for 3–7 items. Convert sequences to numbered lists and comparisons to tables |
| Tables with 8+ columns | Unreadable on mobile. Users scroll horizontally (and they won't) | Max 5 columns. Split into multiple smaller tables if needed |
| Callout overload | When everything is "important," nothing is. 5 callouts in one section = visual noise | Max 1 callout per 500 words. Reserve for genuinely critical information |
| No formatting at all | Walls of text. 80% of readers won't finish the article | Apply the 300-word rule. Add visual elements |
| Inconsistent list items | "Configure settings" / "You should also check your email" / "Dashboard" — mixed grammar | Enforce parallel structure: all items start with the same part of speech |
| Empty table cells | Holes in a comparison table look lazy and incomplete | Use "N/A" or "—" with a brief reason. Never leave cells blank |
Part 4 — Bad vs. Good Examples
- ❌ Paragraph-Only Content
- ✅ Properly Formatted Content
How to Choose a CRM
Choosing a CRM involves considering several factors. First, you need to think about your budget. Different CRMs have different pricing structures. Some offer free tiers while others start at $29 per month. You also need to consider the size of your team. Some CRMs are designed for solo users while others are built for enterprise teams of 500+. Integration with your existing tools is another important factor. You should check whether the CRM integrates with your email platform, your calendar, and your project management tool. Finally, consider the learning curve. Some CRMs require weeks of training while others can be set up in an afternoon.
(120 words in one paragraph. Four distinct comparison dimensions crammed into flowing text. A reader looking for "pricing" has to read the entire paragraph. Impossible to scan.)
How to Choose a CRM
Evaluate every CRM against these four factors before committing:
| Factor | What to Check | Example |
|---|---|---|
| Budget | Free tier availability, per-seat pricing, annual vs monthly billing | Mailchimp: free for 500 contacts; HubSpot: free CRM, paid features from $20/mo |
| Team Size | Solo, small team (2–20), or enterprise (50+) | Zoho: best for 2–10 person teams; Salesforce: built for enterprise |
| Integrations | Email, calendar, project management tool compatibility | Check native integrations first — third-party connectors add cost and complexity |
| Learning Curve | Time from signup to productive use | HubSpot: ~2 hours; Salesforce: ~2 weeks with training |
If you're bootstrapped, filter by budget first. If you're scaling fast, filter by team size. Don't evaluate 20 CRMs on all factors — narrow to 3 candidates on your #1 factor, then compare the rest.
(Same information, dramatically more useful. A reader looking for "pricing" finds it in 2 seconds. Scannable, comparable, actionable.)
Part 5 — AI Collaboration Guidelines
AI defaults to paragraphs. It will write 5 comparison points as flowing text when they should be a table. It will list 8 features in a sentence when they should be a bulleted list. Your editing job is to restructure AI output into the correct format.
The "Format Restructurer" Prompt
Role: Content Formatting Specialist Task: Restructure this draft for web readability. Rules:
- Convert any comparison of 2+ items to a table
- Convert any sequence of steps to a numbered list
- Convert any group of 3–7 features/options to a bulleted list
- Add a callout (:::tip, :::warning, or :::important) for the single most critical takeaway
- Ensure no more than 300 consecutive words of paragraph text without a visual break
- Keep all list items under 2 lines with parallel grammatical structure Input: [Paste Draft]
The "Format Audit" Prompt
Role: UX Content Reviewer Task: Audit this article for formatting issues.
- Count consecutive paragraph-only words. Flag any section exceeding 300 words without a non-paragraph element.
- Identify information currently in paragraph form that would be clearer as a list or table.
- Check for callout overuse (more than 1 per 500 words).
- Verify all list items use parallel structure.
- Check all tables have ≤5 columns and no blank cells. Input: [Paste Draft]
Part 6 — Output Checklist
- Decision framework: You know when to use a list, table, callout, or paragraph.
- 300-word rule: No section of 300+ consecutive words without a non-paragraph element.
- List discipline: Lists have 3–7 items with parallel structure and bold lead keywords.
- Table clarity: Tables have ≤5 columns, clear headers, no blank cells.
- Callout restraint: Maximum 1 callout per 500 words, never stacked consecutively.
- Dynamic rhythm: Your article alternates between paragraphs, lists, tables, and callouts.
Internal use only. Do not distribute externally. For questions or suggested updates, raise with the content lead.